Software Development with Scrum: A Bibliometric Analysis and Profile

Introduction of the Scrum approach into software engineering has changed the way software is being developed. The Scrum approach emphasizes the active end-user involvement, embracing of change, and /iterative delivery of products. Our study showed that Scrum has different variants or is used in combination with different methods. Some tools not normally used in the conventional software approaches, like gamification, content analysis and grounded theory are also employed. However, Scrum like other software development approach focuses on improvement of software process, software quality, business value, performance, usability and efficiency and at the same time to reduce cost, risk and uncertainty. Contrary to some conventional approaches it also strives to boost soft factors like agility, trust, motivation, responsibility and transparency. The bibliometric synthetic scoping study revealed seven main research themes concerned with the Scrum research

Natural user interfaces and development of application for multi - touch devices

This thesis describes multi-touch technology and devices that use this technology. It concentrates on Microsoft Surface, interactive multi-touch table and presents the Surface Web Gallery application, which was built for the device. It's divided into seven chapters. The first chapter briefly covers the development of user interfaces. It focuses mainly on the disadvantages of graphical user interfaces and on the problems users face when working with a computer. It presents the advantages of multi-touch devices and natural user interfaces, which are much more user friendly. The second chapter presents multi-touch technology along with its 25-year history. Following that are the advantages and disadvantages of using this technology. The third chapter focuces on Microsoft Surface – a table shaped multi-touch device, which is capable of detecting many simultaneous contacts at once. Some of the key features of the device are: estetic design, appealing user interface and simplicity of usage. The chapter contains the device description, its history and information about its functionality. The main object of the fourth and fifth chapters is the Galis information system along with its web part – Spletna galerija, on both of which the author collaborated on as a developer. Galis is an information system inteded for documenting cultural heritage and publishing this information on the internet. The Spletna galerija portal allows Galis users to publish collections, articles, publications and exhibition openings. Spletna galerija is also the basis for the Surface Web Gallery, which is the main object of his thesis. The sixth chapter presents the Surface Web Gallery application, which was developed for the Microsoft Surface device. The application represents a modified version of Spletna galerija, which allows the user to browse collections, artwork types, authors and museums. The user can also play a puzzle game. The application has a simple design and The sixth chapter presents the Surface Web Gallery application, which was developed for the Microsoft Surface device. The application represents a modified version of Spletna galerija, which allows the user to browse collections, artwork types, authors and museums. The user can also play a puzzle game. The application has a simple design and is easy to use. Only hands are required to use the application since the Microsoft Surface device detects finger movements and gestures. The thesis is concluded with a final seventh chapter. The ending summarizes the findings of previous chapters and presents the advantages of natural user interfaces and multi-touch devices. It also describes the shortcomings of the Surface Web Gallery application along with plans for the future

Code smells: A Synthetic Narrative Review

Code smells are symptoms of poor design and implementation choices, which might hinder comprehension, increase code complexity and fault-proneness and decrease maintainability of software systems. The aim of our study was to perform a triangulation of bibliometric and thematic analysis on code smell literature production. The search was performed on Scopus (Elsevier, Netherlands) database using the search string “code smells” which resulted in 442 publications. The Go-to statement was the first bad code smells identified in software engineering history in 1968. The literature production trend has been positive. The most productive countries were the United States, Italy and Brazil. Eight research themes were identified: Managing software maintenance, Smell detection-based software refactoring, Architectural smells, Improving software quality with multi-objective approaches, Technical debt and its instance, Quality improvement/assurance with mining software repositories, Programming education, Integrating the concepts of anti-pattern, design defects and design smells. Some research gaps also emerged, namely, New uncatalogued smell identification; Smell propagation from architectural, design, code to test, and other possible smells; and Identification of good smells. The results of our study can help code smell researchers and practitioners understand the broader aspects of code smells research and its translation to practice

Code smells: A Synthetic Narrative Review

Code smells are symptoms of poor design and implementation choices, which might hinder comprehension, increase code complexity and fault-proneness and decrease maintainability of software systems. The aim of our study was to perform a triangulation of bibliometric and thematic analysis on code smell literature production. The search was performed on Scopus (Elsevier, Netherlands) database using the search string “code smells” which resulted in 442 publications. The Go-to statement was the first bad code smells identified in software engineering history in 1968. The literature production trend has been positive. The most productive countries were the United States, Italy and Brazil. Eight research themes were identified: Managing software maintenance, Smell detection-based software refactoring, Architectural smells, Improving software quality with multi-objective approaches, Technical debt and its instance, Quality improvement/assurance with mining software repositories, Programming education, Integrating the concepts of anti-pattern, design defects and design smells. Some research gaps also emerged, namely, New uncatalogued smell identification; Smell propagation from architectural, design, code to test, and other possible smells; and Identification of good smells. The results of our study can help code smell researchers and practitioners understand the broader aspects of code smells research and its translation to practice